From: Eli Zaretskii <eliz@gnu.org>
Date: Wed, 25 Apr 2001 21:45:52 +0000 (+0000)
Subject: Document byte-debug-flag.
X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1~1^2~40557
X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=1bf708f0fcefb103a5e902226d3fde01e6022d92;p=emacs.git

Document byte-debug-flag.
---

diff --git a/etc/DEBUG b/etc/DEBUG
index a4786082ebe..fa32646e71b 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -396,6 +396,15 @@ Once you discover the corrupted Lisp object or data structure, it is
 useful to look at it in a fresh Emacs session and compare its contents
 with a session that you are debugging.
 
+** Debugging problems with non-ASCII characters
+
+If you experience problems which seem to be related to non-ASCII
+characters, such as \201 characters appearing in the buffer or in your
+files, set the variable byte-debug-flag to t.  This causes Emacs to do
+some extra checks, such as look for broken relations between byte and
+character positions in buffers and strings; the resulting diagnostics
+might pinpoint the cause of the problem.
+
 ** Some suggestions for debugging on MS Windows:
 
    (written by Marc Fleischeuers, Geoff Voelker and Andrew Innes)